Formal tone

Technical documentation is typically written in a formal tone. It is meant to be a clear and concise source of information for technical professionals. Here are some characteristics of a formal tone in technical documentation:

1. Objective: Technical documentation should be objective and unbiased, presenting information in a neutral manner. Personal opinions and subjective language should be avoided.

2. Precise: Technical documentation should be precise and accurate, using specific language to convey precise meanings. It is important to clearly define terms and avoid vague or ambiguous language.

3. Formal: Technical documentation should use formal language and avoid slang, colloquialisms, or jargon that may not be familiar to all readers.

4. Concise: Technical documentation should be concise and to the point, avoiding unnecessary information or filler words. It should focus on the key points and present them clearly and efficiently.

By maintaining a formal tone, technical documentation can effectively convey information to its intended audience and be a reliable source of technical knowledge.

Examples

1. The report shows the list of feedback received in the selected date range.
2. It works effectively for SSO readers.